Handling of multi-access PDU session when inter-system change

ABSTRACT

A method of handling multi-access (MA) Protocol data unit (PDU) session under inter-system change is proposed. An MA PDU session uses one 3GPP access network or one non-3GPP access network at a time, or simultaneously one 3GPP access network and one non-3GPP access network. The UE and network can support Access Traffic Steering Switching and Splitting (ATSSS) functionalities to distribute traffic over 3GPP access and non-3GPP access for the established MA PDU session. Upon intersystem change from 5GS to EPS over the 3GPP access, if interworking with EPS is not supported, the MA PDU session is maintained in 5GS over the non-3GPP access type. Data traffic over of the MA PDU session over the 3GPP access type is transferred to the non-3GPP access type.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 119 from U.S.Provisional Application No. 62/862,755, entitled “Enhancement forMulti-Access PDU Session”, filed on Jun. 18, 2019; U.S. ProvisionalApplication No. 62/866,712, entitled “Handling of MA PDU Session WhenInter-System Change”, filed on Jun. 26, 2019, the subject matter ofwhich is incorporated herein by reference.

TECHNICAL FIELD

The disclosed embodiments relate generally to wireless communication,and, more particularly, to method of handling of Multi-Access (MA) PDUsession during inter-system change between 5G system (5GS) and 4G LTEsystems.

BACKGROUND

The wireless communications network has grown exponentially over theyears. A Long-Term Evolution (LTE) system offers high peak data rates,low latency, improved system capacity, and low operating cost resultingfrom simplified network architecture. LTE systems, also known as the 4Gsystem, also provide seamless integration to older wireless network,such as GSM, CDMA and Universal Mobile Telecommunication System (UMTS).In LTE systems, an evolved universal terrestrial radio access network(E-UTRAN) includes a plurality of evolved Node-Bs (eNodeBs or eNBs)communicating with a plurality of mobile stations, referred to as userequipments (UEs). The 3^(rd) generation partner project (3GPP) networknormally includes a hybrid of 2G/3G/4G systems. The Next GenerationMobile Network (NGMN) board, has decided to focus the future NGMNactivities on defining the end-to-end requirements for 5G new radio (NR)systems.

In 5G/NR, a Protocol Data Unit (PDU) session defines the associationbetween the UE and the data network that provides a. PDU connectivityservice. The PDU session establishment is a parallel procedure of PDNconnection (bearer) procedure in 4G/LTE. Each PDU session is identifiedby a PDU session ID (PSI), and may include multiple QoS flows and QoSrules. Each PDU session can be established via a 5G Access Network(e.g., 3GPP radio access network (RAN), or via a non-3GPP RAN). Thenetwork/UE can initiate different PDU session procedures, e.g., PDUsession establishment, PDU session modification, and PDU sessionrelease. Due to new radio conditions, load balancing, or due to specificservice, different handover procedures and intersystem change are usedto handover a UE from a source 5G access network to a target 5G accessor to a target 4G access network.

Operators are seeking ways to balance data traffic between mobilenetworks and non-3GPP access in a way that is transparent to users andreduces mobile network congestion. In 5GS, UEs that can besimultaneously connected to both 3GPP access and non-3GPP access (using3GPP NAS signalling), thus the 5GS able to take advantage of thesemultiple accesses to improves the user experience, optimizes the trafficdistribution across various accesses. Accordingly, 3GPP introducedMulti-Access Access (MA) PDU session in 5GS. A MA PDU session uses one3GPP access network or one non-3GPP access network at a time, orsimultaneously one 3GPP access network and one non-3GPP access network.In addition, the UE and network can support Access Traffic SteeringSwitching and Splitting (ATSSS) functionalities to distribute trafficover 3GPP access and non-3GPP access for the established MA PDU session.

However, UE behavior is undefined on how to handle the MA PDU sessionwhen inter-system changes from 5GS to EPS. A solution is sought.

SUMMARY

A method of handling multi-access (MA) Protocol data unit (PDU) sessionunder inter-system change is proposed. An MA PDU session uses one 3GPPaccess network or one non-3GPP access network at a time, orsimultaneously one 3GPP access network and one non-3GPP access network.The UE and network can support Access Traffic Steering Switching andSplitting (ATSSS) functionalities to distribute traffic over 3GPP accessand non-3GPP access for the established MA PDU session. Upon intersystemchange from 5GS to EPS over the 3GPP access, if interworking with EPS issupported, the 3GPP part of an MA PDU session is transferred to a PDNconnection, and the non-3GPP part of the MA PDU session is released. TheQoS flows of the MA PDU session over both 3GPP access type and non-3GPPaccess type are transferred to the EPS bearer contexts of thecorresponding PDN connection. On the other hand, if interworking withEPS is not supported, the MA PDU session is maintained in 5GS overnon-3GPP access type. Data traffic of the MA PDU session over the 3GPPaccess type is transferred to the non-3GPP access type.

In one embodiment, a UE performs registration in a 5G mobilecommunication network. The UE establishes a multi-access (MA) Protocoldata unit (PDU) session in 5G system (5GS). The MA PDU session has a PDUsession ID (PSI) and is established over both a first radio accesstechnology (RAT) access type and a second RAT access type. The UEperforms an inter-system change from 5GS to evolved packet system (EPS).The UE transfers the MA PDU session to a corresponding Packet DataNetwork (PDN) connection over the first RAT access type in EPS. The MAPDU session over the first RAT access type is transferred to the PDNconnection and the MA PDU session over the second RAT access type isreleased.

In another embodiment, a UE performs registration in a 5G mobilecommunication network. The UE establishes a multi-access (MA) Protocoldata unit (PDU) session in 5G system (5GS). The MA PDU session has a PDUsession ID (PSI) and is established over both a first radio accesstechnology (RAT) access type and a second RAT access type. The UEperforms an inter-system change from 5GS to evolved packet system (EPS).The UE determines that the MA PDU session is not converted to acorresponding protocol data network (PDN) connection in EPS. Datatraffic over the first RAT access type of the MA PDU session is thentransferred to the second RAT access type in 5GS.

Other embodiments and advantages are described in the detaileddescription below. This summary does not purport to define theinvention. The invention is defined by the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, where like numerals indicate like components,illustrate embodiments of the invention.

FIG. 1 illustrates an exemplary 5G network supporting Multi-AccessProtocol Data Unit (MA PDU) session management with inter-system changein accordance with one novel aspect.

FIG. 2 illustrates simplified block diagrams of a user equipment (UE)and a network entity in accordance with embodiments of the currentinvention.

FIG. 3 illustrates one embodiment of establishing a MA PDU session in5GS after a UE is registered to the network over both 3GPP and non-3GPPaccess type belonging to the same PLMN.

FIG. 4 illustrates one embodiment of establishing a MA PDU session in5GS after a UE is registered to the network over both 3GPP and non-3GPPaccess type belonging to different PLMNs.

FIG. 5 illustrates another embodiment of establishing a MA PDU sessionin 5GS when a UE is registered to one RAT access type and thenregistered to another RAT access type.

FIG. 6 illustrates a simplified block diagram of a UE supporting MPTCPfunctionality operates above the IP layer and/or ATSSS functionalityoperates below the IP layer as a data switching function.

FIG. 7 illustrates one embodiment of inter-system change from 5GS to EPSand QoS flow handling when an MA PDU session is converted to a PDNconnection.

FIG. 8 illustrates a sequence flow between a UE and 5GS and EPS when aMA PDU session is converted to a PDN connection when intersystem changefrom 5GS to EPS in accordance with one novel aspect.

FIG. 9 illustrates one embodiment of inter-system change from 5GS to EPSand QoS flow handling when an MA PDU session is not converted to a PDNconnection.

FIG. 10 illustrates a sequence flow between a UE and 5GS and EPS when aMA PDU session is not converted to a PDN connection when intersystemchange from 5GS to EPS in accordance with one novel aspect.

FIG. 11 is a flow chart of one method of supporting MA PDU session withintersystem change in accordance with one novel aspect of the presentinvention.

FIG. 12 is a flow chart of another method of supporting MA PDU sessionwith intersystem change in accordance with one novel aspect of thepresent invention.

DETAILED DESCRIPTION

Reference will now be made in detail to some embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings.

FIG. 1 illustrates an exemplary 5G network 100 supporting Multi-AccessProtocol Data Unit (MA PDU) session management with inter-system changein accordance with one novel aspect. 5G new radio (NR) network 100comprises a user equipment UE 101, a 3GPP radio access network RAN 102,a non-3GPP radio access network RAN 103, an Access and MobilityManagement Function (AMF) 110, a Session Management Function (SMF) 111,an Non-3GPP Interworking Function (N3IWF) 112, a User Plane Function(UPF) 113, and a 5G core (5GC) or Evolved Packet core (EPC) data network120. The AMF communicates with the base station, SMF and UPF for accessand mobility management of wireless access devices in mobilecommunication network 100. The SMF is primarily responsible forinteracting with the decoupled data plane, creating, updating andremoving Protocol Data Unit (PDU) sessions and managing session contextwith the UPF. The N3IWF functionality interfaces to 5G core networkcontrol plane functions, responsible for routing messages outside 5GRAN.

In Access Stratum (AS) layer, RAN provides radio access for UE 101 via aradio access technology (RAT). In Non-Access Stratum (NAS) layer, AMFand SMF communicate with RAN and 5GC/EPC for access and mobilitymanagement and PDU session management of wireless access devices in 5Gnetwork 100. 3GPP Radio access network RAN 102 may include base stations(gNBs or eNBs) providing radio access for UE 101 via various 3GPP RATsincluding 5G, 4G, and 3G/2G. Non-3GPP radio access network RAN 103 mayinclude access points (APs) providing radio access for UE 101 vianon-3GPP RAT including WiFi. UE 101 can obtain access to data network120 through 3GPP access 102, AMF 110, SMF 111, and UPF 113. UE 101 canobtain access to data network 120 through non-3GPP access 103, N3IWF112, AMF 110, SMF 111, and UPF 113. UE 101 may be equipped with a singleradio frequency (RF) module or transceiver or multiple RF modules ortransceivers for services via different RATs/CNs. UE 101 may be a smartphone, a wearable device, an Internet of Things (IoT) device, a tablet,etc.

5GS networks are packet-switched (PS) Internet Protocol (IP) networks.This means that the networks deliver all data traffic in IP packets, andprovide users with Always-On IP Connectivity. When UE joins an EPSnetwork, a Packet Data Network (PDN) address (i.e., the one that canused on the PDN) is assigned to the UE for its connection to the PDN. In4G, EPS has defined a Default EPS Bearer to provide the IP Connectivitythat is Always-On. In 5G, a Protocol Data Unit (PDU) sessionestablishment procedure is a parallel procedure or a PDN connectionprocedure in 4G. A PDU session defines the association between the UEand the data network that provides a PDU connectivity service. Each PDUsession is identified by a PDU session ID, and may include multiple QoSflows and QoS rules. In 5G network, QoS flow is the finest granularityfor QoS management to enable more flexible QoS control. The concept ofQoS flow in 5G is like EPS bearer in 4G.

Each PDU session can be established over a 3GPP RAN, or over a non-3GPPRAN for radio access. 5G Session management (5GSM) for PDU sessions overboth 3GPP access and non-3GPP access are managed by AMF and SMF via NASsignaling. Operators are seeking ways to balance data traffic betweenmobile networks and non-3GPP access in a way that is transparent tousers and reduces mobile network congestion. In 5GS, UEs that can besimultaneously connected to both 3GPP access and non-3GPP access (using3GPP NAS signalling), thus the 5GS able to take advantage of thesemultiple accesses to improves the user experience, optimizes the trafficdistribution across various accesses. Accordingly, 3GPP introducedMulti-Access (MA) PDU session in 5GS. A MA PDU session uses one 3GPPaccess network or one non-3GPP access network at a time, orsimultaneously one 3GPP access network and one non-3GPP access network.In addition, the UE and the network can support Access Traffic SteeringSwitching and Splitting (ATSSS) functionalities to distribute trafficover 3GPP access and non 3GPP access for the established MA PDU session.

When a MA PDU session established in 5GS, it includes a number of QoSflows in Non-Access Stratum (NAS) layer. Each QoS flow may be mapped toa corresponding EPS bearer. In addition, based on ATSSS rules, each QoSflow may use 3GPP access or non-3GPP access. When a QoS flow is added,the network can provide a QoS flow description IE to the UE, whichcomprises a list of QoS flow descriptions. Each QoS flow descriptioncomprises a QoS flow identifier (QFI), a QoS flow operation code, anumber of QoS flow parameters, and a QoS flow parameters list. Eachparameter included in the parameters list consists of a parameteridentifier that identifies the corresponding parameter. One of theparameter identifiers is the EPS bearer identity (EBI), which is used toidentify the EPS bearer that is mapped to or associated with the QoSflow. However, if an MA PDU session does not support interworking withEPS, then there are no associated ESM parameters, e.g., EBI, mapped EPSbearer contexts, when inter-system change from 5GS to EPS over 3GPPaccess.

After inter-system change from N1 (5GS) mode to S1 (4G, EPS) mode, ifinterworking with EPS is supported, then a PDU session in 5GS istransferred to a corresponding PDN connection in EPS, and QoS flows ofthe PDU session are mapped to associated EPS bearers. The default EPSbearer context includes a PDU session identity (PSI), S-NSSAI, sessionAMBR and one or more QoS flow descriptions received in the Protocolconfiguration options IE or Extended protocol configuration options IE,or the default EPS bearer context has association with the PDU sessionidentity, the S-NSSAI, the session-AMBR and one or more QoS flowdescriptions. However, UE behavior is undefined on how to handle a MAPDU session when inter-system changes from 5GS to EPS, regardless ofinterworking with EPS is supported or not.

In accordance with one novel aspect, if interworking with EPS issupported, and if the MA PDU session in 5GS is over both 3GPP andnon-3GPP access (i.e., the MA PDU session is established and the userplane resources of the MA PDU session on both 3GPP access and non-3GPPaccess are successfully established), upon intersystem change from 5GSto EPS over the 3GPP access, the 3GPP part of the PDU session istransferred to the PDN connection, and the non-3GPP part of the PDUsession is released. The QoS flows of the MA PDU session over both 3GPPaccess and non-3GPP access are transferred to the EPS bearer contexts ofthe corresponding PDN connection. As depicted by arrowed line 131, MAPDU session with PSI=1 in 5GS is transferred to PDN connection #1 inEPS. All the QoS flows with EBI assigned over 3GPP and non-3GPP accessare transferred to the PDN connection #1 in EPS. User plane resources ofthe MA PDU session over non-3GPP access are released in 5GS via a PDUsession release procedure, and the ATSSS rules are released. On theother hand, if interworking with EPS is not supported, and if the MA PDUsession in 5GS is over both 3GPP and non-3GPP access, upon intersystemchange from 5GS to EPS over the 3GPP access, the MA PDU session ismaintained in 5GS over non-3GPP access, and data traffic of the MA PDUsession over 3GPP access is moved to non-3GPP access in 5GS. As depictedby arrowed line 132, MA PDU session with PSI=1 in 5GS is maintained in5GS and not transferred to any PDN connection in EPS. Optionally,through a PDU session modification procedure initiated by the network orby the UE, data traffic of the MA PDU session over 3GPP access is movedto non-3GPP access. In some steering modes, the 3GPP traffic can bemoved to non-3GPP access by the UE directly, without the PDU sessionmodification procedure.

FIG. 2 illustrates simplified block diagrams of wireless devices, e.g.,a UE 201 and a network entity 211 in accordance with embodiments of thecurrent invention. Network entity 211 may be a base station and/or anAMF/SMF. Network entity 211 has an antenna 215, which transmits andreceives radio signals. A radio frequency RF transceiver module 214,coupled with the antenna, receives RF signals from antenna 215, convertsthem to baseband signals and sends them to processor 213. RF transceiver214 also converts received baseband signals from processor 213, convertsthem to RF signals, and sends out to antenna 215. Processor 213processes the received baseband signals and invokes different functionalmodules to perform features in base station 211. Memory 212 storesprogram instructions and data 220 to control the operations of basestation 211. In the example of FIG. 2, network entity 211 also includesprotocol stack 280 and a set of control functional modules and circuit290. PDU session and PDN connection handling circuit 231 handles PDU/PDNestablishment and modification procedures. QoS and EPS bearer managementcircuit 232 creates, modifies, and deletes QoS and EPS bearers for UE.Configuration and control circuit 233 provides different parameters toconfigure and control UE of related functionalities including mobilitymanagement and PDU session management, handover module 234 handleshandover and inter-system change functionalities between 5GS and EPS.

Similarly, UE 201 has memory 202, a processor 203, and radio frequency(RF) transceiver module 204. RF transceiver 204 is coupled with antenna205, receives RF signals from antenna 205, converts them to basebandsignals, and sends them to processor 203. RF transceiver 204 alsoconverts received baseband signals from processor 203, converts them toRF signals, and sends out to antenna 205. Processor 203 processes thereceived baseband signals and invokes different functional modules andcircuits to perform features in UE 201. Memory 202 stores data andprogram instructions 210 to be executed by the processor to control theoperations of UE 201. Suitable processors include, by way of example, aspecial purpose processor, a digital signal processor (DSP), a pluralityof micro-processors, one or more micro-processor associated with a DSPcore, a controller, a microcontroller, application specific integratedcircuits (ASICs), file programmable gate array (FPGA) circuits, andother type of integrated circuits (ICs), and/or state machines. Aprocessor in associated with software may be used to implement andconfigure features of UE 201.

UE 201 also comprises a set of functional modules and control circuitsto carry out functional tasks of UE 201. Protocol stacks 260 compriseNon-Access-Stratum (NAS) layer to communicate with an AMF/SMF/MME entityconnecting to the core network, Radio Resource Control (RRC) layer forhigh layer configuration and control, Packet Data ConvergenceProtocol/Radio Link Control (PDCP/RLC) layer, Media Access Control (MAC)layer, and Physical (PHY) layer. System modules and circuits 270 may beimplemented and configured by software, firmware, hardware, and/orcombination thereof. The function modules and circuits, when executed bythe processors via program instructions contained in the memory,interwork with each other to allow UE 201 to perform embodiments andfunctional tasks and features in the network.

In one example, system modules and circuits 270 comprise PDU session andPDN connection handling circuit 221 that performs PDU session and PDNconnection establishment and modification procedures with the network, aQoS flow and EPS bearer handling circuit 222 that manages, creates,modifies, and deletes QoS flows and mapped EPS bearer contexts, a configand control circuit 223 that handles configuration and controlparameters for mobility management and session management, and ahandover module that handles handover and intersystem change. In oneexample, if interworking is supported and if the MA PDU session is overboth 3GPP and non-3GPP access, upon inter-system change from 5GS to EPSover 3GPP access, the 3GPP part of the PDU session is transferred to thePDN connection, and the non-3GPP part of the PDU session is released.The QoS flows of the MA PDU session over both 3GPP access and non-3GPPaccess are transferred to the EPS bearer contexts of the correspondingPDN connection. In another example, if interworking is not supported andif the MA PDU session is over both 3GPP and non-3GPP access, uponinter-system change from 5GS to EPS over 3GPP access, the MA PDU sessionis maintained in 5GS over non-3GPP access, and data traffic of the MAPDU session over 3GPP access is moved to non-3GPP access.

FIG. 3 illustrates one embodiment of establishing a MA PDU session in5GS after a UE is registered to the network over both 3GPP and non-3GPPaccess type belonging to the same PLMN. UE 301 is registered over 3GPPaccess type to PLMN1 through a 3GPP base station gNB 302. UE 301 is alsoregistered over non-3GPP access type to PLMN1 through a non-3GPP accesspoint AP 303. UE 301 establishes a MA PDU session by initiating a PDUsession establishment procedure with the network over either 3GPP ornon-3GPP access type. The activation of the MA PDU connectivity servicerefers to the establishment of user-plane resources on both 3GPP accessand non-3GPP access. Since UE 301 is registered to the network over bothRAT access types belonging to the same PLMN1, the MA PDU session withPSI=1 is established over both 3GPP and non-3GPP access types, and thenthe user-plane resources are established over both 3GPP and non-3GPPaccess types.

FIG. 4 illustrates one embodiment of establishing a MA PDU session in5GS after a UE is registered to the network over both 3GPP and non-3GPPaccess type belonging to different PLMNs. UE 401 is registered over 3GPPaccess type to a first PLMN1 through a 3GPP base station gNB 402. UE 401is also registered over non-3GPP access type to a second PLMN2 through anon-3GPP access point AP 403. UE 401 establishes a MA PDU session byinitiating a PDU session establishment procedure with the network overone of the access types, e.g., 3GPP access type. For example, UE 401sends a PDU SESSION ESTABLISHMENT REQUEST message to gNB 402, with arequest type IE set to “MA PDU request” and with PSI=1. The user planeresource on 3GPP access is then established. Next, UE 401 sends anotherPDU SESSION ESTABLISHMENT REQUEST message to AP 403, with a request typeIE set to “MA PDU request” and with the same PSI=1. The user planeresource on non-3GPP access is then established. Since UE 401 isregistered to the network over both RAT access types belonging todifferent PLMNs, the MA PDU session with PSI=1 is first established over3GPP access type and then established over non-3GPP access type in twoseparate steps.

FIG. 5 illustrates another embodiment of establishing a MA PDU sessionin 5GS when a UE is registered to one RAT access type and thenregistered to another RAT access type to the same PLMN. UE 501 isregistered over 3GPP access type to a first PLMN1 through a 3GPP basestation gNB 502. UE 501 is not registered over non-3GPP access type toPLMN1. UE 501 then establishes a MA PDU session by initiating a PDUsession establishment procedure with the network over 3GPP access type.For example, UE 501 sends a PDU SESSION ESTABLISHMENT REQUEST message togNB 502, with a request type IE set to “MA PDU request” and with PSI=1.The user plane resource on 3GPP access is then established. Later, UE501 is registered over non-3GPP access type to the same PLMN1 through anon-3GPP access point AP 503. UE 501 sends another PDU SESSIONESTABLISHMENT REQUEST message to AP 503, with a request type IE set to“MA PDU request” and with the same PSI=1. The user plane resource onnon-3GPP access is then established. As a result, UE 501 establishes theMA PDU session to the same PLMN1 with PSI=1 over both 3GPP access typeand non-3GPP access type in two separate steps.

FIG. 6 illustrates a simplified block diagram of a UE supporting MPTCPfunctionality operates above the IP layer and/or ATSSS functionalityoperates below the IP layer as a data switching function. The UE and thenetwork can support one or more of the steering functionalities for MAPDU session. The MPTCP functionality operates above the IP layer, whilethe ATSSS-LL functionality operates below the IP layer as a dataswitching function. As depicted in FIG. 6, in higher-layer, the MPTCPfunctionality checks the ATSSS rules, and MPTCP flows (TCP flows fromapps allowed to use MPTCP) are split into subflows bound to different IPin middle-layer (e.g., IP stack) and low-layer and then steered orswitched to non-3GPP access or 3GPP access. For non MPTCP flows (e.g.,UDP, TCP, Ethernet flows), in low-layer, the ATSSS-LL functionalitychecks the ATSS rules, and splits, steers, or switches the traffic flowsto non-3GPP or 3GPP access.

In an ATSSS capable UE, the ATSSS-LL requirements are as follows. For anMA PDU session of Ethernet PDU session type, the ATSSS-LL functionalityis mandatory. For an MA PDU session of IPv4, IPv6, or IPv4v6 PDU sessiontype, if the UE does not support the MPTCP functionality, the ATSSS-LLfunctionality is mandatory. If the UE supports the MPTCP functionality,only the active-standby steering mode of the ATSSS-LL functionality ismandatory. All other steering modes are optional. The ATSSS rules areprovided by the network in 5GSM messages, e.g., in PDU SESSIONESTABLISHMENT ACCEPT or PDU SESSION MODIFICATION COMMAND message. Theparameters of the ATSSS rules includes rule precedence that determinesthe order in which the ATSSS rule is evaluated in UE, trafficdescriptor, application descriptor, IP descriptors, access selectiondescriptors, steering mode that identifies the steering mode(active-standby, smallest delay, load balancing, priority based) thatshould be applied for the matching traffic, and steering functionalitythat identifies whether the MPTCP functionality or the ATSSS-LLfunctionality should be applied for the matching traffic. Examples ofATSSS rules include: 1. “Traffic Descriptor: UDP, DestAddr 1.2.3.4”,“Steering Mode: Active-Standby, Active=3GPP, Standby=non-3GPP”—This rulemeans “steer UDP traffic with destination IP address 1.2.3.4 to theactive access (3GPP), if available. If the active access is notavailable, use the standby access (non-3GPP)”. 2. “Traffic Descriptor:TCP, DestPort 8080”, “Steering Mode: Smallest Delay”—This rule means“steer TCP traffic with destination port 8080 to the access with thesmallest delay”. The UE needs to measure the RTT over both accesses, inorder to determine which access has the smallest delay. “TrafficDescriptor: Application-1”, “Steering Mode: Load-Balancing, 3GPP=20%,non-3GPP=80%”, “Steering Functionality: MPTCP”—This rule means “send 20%of the traffic of Application-1 to 3GPP access and 80% to non-3GPPaccess by using the MPTCP functionality”.

FIG. 7 illustrates one embodiment of inter-system change from 5GS to EPSand QoS flow handling when an MA PDU session is converted to a PDNconnection. In 5GS, a UE establishes a MA PDU session with PSI=1, overboth 3GPP and non-3GPP access. The MA PDU session is configured withthree QoS flows and certain ATSSS rules for data traffic distribution.The granularity for ATSSS steering feature is per service data flow(SDF), not per QoS flow. The scope of SDF is independent from QoS flow.A QoS flow can include one or multiple SDFs, and an SDF can bedistributed over one or multiple QoS flows. The ATSSS steering functiondecides which access (3GPP or non-3GPP) to send the traffic of an SDF.Upon inter-system change from 5GS to EPS, the user plane resource of theMA PDU session over 3GPP access is transferred to a corresponding PDNconnection in EPS, and the user plane resource of the MA PDU sessionover non-3GPP access is released. All the three QoS flows of the MA PDUsession are transferred to the corresponding PDN connection in EPS. ThePDN connection 1 in EPS includes two EPS bearers: a default EPS bearerwith EBI=1 is associated with QoS flow1 and QoS flow2, and a dedicatedEPS bearer with EBI=2 is associated with QoS flow3.

FIG. 8 illustrates a sequence flow between a UE 801 and 5GS and EPS whena MA PDU session is converted to a PDN connection when intersystemchange from 5GS to EPS in accordance with one novel aspect. In step 811,UE 801 registers with the 5GS network over 3GPP access type. In step812, UE 801 registers with the 5GS network over non-3GPP access type.The registered 5GS network belong to the same PLMN. In step 821, UE 801initiates a PDU session establishment procedure by sending a PDU SESSIONESTABLISHMENT REQUEST message over either access type, to establish anMA PDU session with a request type IE set to “MA PDU request” and withPSI=1. In step 822, UE 801 receives a PDU SESSION ESTABLISHMENT ACCEPTmessage from the network over a corresponding access type, which carriesAccess Traffic Steering Switching and Splitting (ATSSS) rule. In step831, the MA PDU session with PSI=1 is established between UE 801 and the5GS over both 3GPP and non-3GPP access types. The ATSSS rules provideparameters for traffic steering, switching, and splittingfunctionalities between the 3GPP and non-3GPP access. Note that theestablishment for an MA PDU session may require multiple steps, e.g., ifthe UE is registered with different PLMNs over different RATS.

In step 841, an inter-system change occurs for UE 801 to handover from5GS to EPS. When UE 801 moves from 5GS to EPS, for both idle mode andconnected mode mobility, the MA PDU session is moved to a correspondingPDN connection in EPS. The SMF triggers a PDU session release procedureto release the MA PDU session over non-3GPP access in 5GS, e.g., MA PDUsession's user plane resource on non-3GPP access. In step 842, thenetwork sends a PDU SESSION RELEASE COMMAND message to UE 801, with anaccess type IE set to “non-3GPP” and with PSI=1. In step 843, UE 801transmits a PDU SESSION RELEASE COMPLETE message to the network. Theuser plane resource on non-3GPP access of the MA PDU session is thenreleased, and the ATSSS rules are also released. Note that the PDUsession release procedure of steps 842-843 may occur after step 851. Inaddition, the non-3GPP access part of the MA PDU session can be releasedlocally by the UE without performing the PDU session release procedure.In step 851, the MA PDU session over 3GPP access is converted to a PDNconnection in EPS for 3GPP access. Note that QoS flows with allocatedEBIs of the MA PDU session using both 3GPP access and non-3GPP accessare transferred to EPS bearer contexts of the corresponding PDNconnection over 3GPP access. UE and SMF remove ATSSS related contexts,e.g., ATSSS rules, and measurement assistance information.

FIG. 9 illustrates one embodiment of inter-system change from 5GS to EPSand QoS flow handling when an MA PDU session is not converted to a PDNconnection. In 5GS, a UE establishes a MA PDU session with PSI=1, overboth 3GPP and non-3GPP access. The MA PDU session is configured withthree QoS flows and certain ATSSS rules for data traffic distribution:QoS flow1 and QoS flow2 are created for 3GPP access, QoS flow3 iscreated for non-3GPP access. However, the UE does not supportinterworking for the MA PDU session, e.g., the QoS flows of the MA PDUsession are not allocated with mapping EPS bearers of a correspondingPDN connection in EPS. Upon inter-system change from 5GS to EPS, the MAPDU session is maintained in 5GS and is not transferred to any PDNconnection in EPS. The UE can move the data traffic of the MA PDUsession from 3GPP access to non-3GPP access based on the steering modeof the ATSSS rule. For example, if the steering mode is active-standby,then UE can steer the SDF by using the active access if available, orusing the standby access if the active access is not available. If thesteering mode is smallest delay, then UE can steer the SDF using theaccess network with the smallest RTT. If the steering mode is loadbalancing, then UE can steer the SDF across both 3GPP and non-3GPPaccess. If only one access (e.g., non-3GPP) is available, the UE steersthe SDF by using the available access. The network can also move thedata traffic of the MAPDU session from 3GPP access to non-3GPP accessvia a PDU session modification procedure.

FIG. 10 illustrates a sequence flow between a UE and 5GS and EPS when aMA PDU session is not converted to a PDN connection when intersystemchange from 5GS to EPS in accordance with one novel aspect. In step1011, UE 1001 registers with the 5GS network over 3GPP access type. Instep 1012, UE 1001 registers with the 5GS network over non-3GPP accesstype. The registered 5GS network belong to the same PLMN. In step 1021,UE 1001 initiates a PDU session establishment procedure by sending a PDUSESSION ESTABLISHMENT REQUEST message over either access type, toestablish an MA PDU session with a request type IE set to “MA PDUrequest” and with PSI=1. In step 1022, UE 1001 receives a PDU SESSIONESTABLISHMENT ACCEPT message from the network over a correspondingaccess type, which carries Access Traffic Steering Switching andSplitting (ATSSS) rule. In step 1031, the MA PDU session with PSI=1 isestablished between UE 1001 and the 5GS over both 3GPP and non-3GPPaccess types. The ATSS rules provide parameters for traffic steering,switching, and splitting functionalities between the 3GPP and non-3GPPaccess. Note that the establishment for an MA PDU session may requiremultiple steps, e.g., if the UE is registered with different PLMNs overdifferent RATS.

In step 1041, an inter-system change occurs for UE 1001 to handover from5GS to EPS. When UE 1001 moves from 5GS to EPS, for both idle mode andconnected mode mobility, the MA PDU session is maintained in 5GS overnon-3GPP access. In step 1042, the network sends a PDU SESSIONMODIFICATION COMMAND message to UE 1001. In step 1043, UE 1001 sends aPDU SESSION MODIFICATION COMPLETE message back to the network. Throughthe PDU session modification procedure, the network can modify thesteering mode in the ATSSS rule so that, data traffic of the MA PDUsession is moved from 3GPP access to non-3GPP access. Note that UE 1001is capable to transfer the data traffic from 3GPP access to non-3GPPaccess by itself without the PDU session modification procedure, e.g.,based on the steering mode in the ATSSS rule.

FIG. 11 is a flow chart of a method of supporting MA PDU session withintersystem change in accordance with one novel aspect of the presentinvention. In step 1101, a UE performs registration in a 5G mobilecommunication network. In step 1102, the UE establishes a multi-access(MA) Protocol data unit (PDU) session in 5G system (5GS). The MA PDUsession has a PDU session ID (PSI) and is established over both a firstradio access technology (RAT) access type and a second RAT access type.In step 1103, the UE performs an inter-system change from 5GS to evolvedpacket system (EPS). In step 1104, the UE converts the MA PDU session toa corresponding Packet Data Network (PDN) connection over the first RATaccess type in EPS. The MA PDU session over the first RAT access type istransferred to the PDN connection and the MA PDU session over the secondRAT access type is released.

FIG. 12 is a flow chart of a method of supporting MA PDU session withintersystem change in accordance with one novel aspect of the presentinvention. In step 1201, a UE performs registration in a 5G mobilecommunication network. In step 1202, the UE establishes a multi-access(MA) Protocol data unit (PDU) session in 5G system (5GS). The MA PDUsession has a PDU session ID (PSI) and is established over both a firstradio access technology (RAT) access type and a second RAT access type.In step 1203, the UE performs an inter-system change from 5GS to evolvedpacket system (EPS). In step 1204, the UE determines that the MA PDUsession is not converted to a corresponding protocol data network (PDN)connection in EPS. Data traffic over the first RAT access type of the MAPDU session is then transferred to the second RAT access type in 5GS.

Although the present invention has been described in connection withcertain specific embodiments for instructional purposes, the presentinvention is not limited thereto. Accordingly, various modifications,adaptations, and combinations of various features of the describedembodiments can be practiced without departing from the scope of theinvention as set forth in the claims.

What is claimed is:
 1. A method, comprising: performing registration bya user equipment (UE) in a 5G mobile communication network; establishinga multi-access (MA) Protocol data unit (PDU) session in 5G system (5GS),wherein the MA PDU session has a PDU session ID (PSI) and is establishedover both a first radio access technology (RAT) access type and a secondRAT access type; performing an inter-system change from 5GS to evolvedpacket system (EPS); and determining that the MA PDU session is notconverted to a corresponding protocol data network (PDN) connection inEPS, wherein data traffic over the first RAT access type of the MA PDUsession is transferred to the second RAT access type in 5GS.
 2. Themethod of claim 1, wherein MA PDU session is modified by anetwork-initiated PDU session modification procedure such that the datatraffic over the first RAT access type of the MA PDU session istransferred to the second RAT access type in 5GS.
 3. The method of claim1, wherein the UE initiates the MA PDU session establishment by sendinga PDU SESSION ESTABLISHMENT REQUEST message with a request type set to“MA PDU request”.
 4. The method of claim 3, wherein the UE receives aPDU SESSION ESTABLISHMENT ACCEPT message, wherein the message carriesAccess Traffic Steering Switching and Splitting (ATSSS) rules from thenetwork.
 5. The method of claim 4, wherein the UE maintains the MA PDUsession in 5GS over the second RAT access type.
 6. The method of claim4, wherein the ATSSS rules are modified upon inter-system change suchthat data traffic over the first RAT access type of the MA PDU sessionis transferred to the second RAT access type.
 7. The method of claim 1,wherein the first RAT access type is 3GPP access, and the second RATaccess type is non-3GPP access.
 8. The method of claim 1, furthercomprising: registering with a same Public Land Mobile Network (PLMN)over the first RAT access type and the second RAT access type.
 9. Themethod of claim 1, further comprising: registering with a first PublicLand Mobile Network (PLMN) over the first RAT access type and a secondPLMN over the second RAT access type.
 10. A User Equipment (UE),comprising: a registration circuit that performs registration in a 5Gmobile communication network; a Protocol Data Unit (PDU) sessionhandling circuit that establishes a multi-access (MA) PDU (MA PDU)session in 5G system (5GS), wherein the MA PDU session has a PDU sessionID (PSI) and is established over both a first radio access technology(RAT) access type and a second RAT access type; an inter-system handlingcircuit that performs an inter-system change from 5GS to evolved packetsystem (EPS), wherein the UE determines that the MA PDU session is notconverted to a corresponding protocol data network (PDN) connection inEPS, wherein data traffic over the first RAT access type of the MA PDUsession is transferred to the second RAT access type in 5GS.
 11. The UEof claim 10, wherein MA PDU session is modified by a network-initiatedPDU session modification procedure such that the data traffic over thefirst RAT access type of the MA PDU session is transferred to the secondRAT access type in 5GS.
 12. The UE of claim 10, wherein the UE initiatesthe MA PDU session establishment by sending a PDU SESSION ESTABLISHMENTREQUEST message with a request type set to “MA PDU request”.
 13. The UEof claim 12, wherein the UE receives a PDU SESSION ESTABLISHMENT ACCEPTmessage, wherein the message carries Access Traffic Steering Switchingand Splitting (ATSSS) rules from the network.
 14. The UE of claim 13,wherein the UE maintains the MA PDU session in 5GS over the second RATaccess type.
 15. The UE of claim 13, wherein the ATSSS rules aremodified upon inter-system change such that data traffic over the firstRAT access type of the MA PDU session is transferred to the second RATaccess type.
 16. The UE of claim 10, wherein the first RAT access typeis 3GPP access, and the second RAT access type is non-3GPP access. 17.The UE of claim 10, wherein the UE registers with a same Public LandMobile Network (PLMN) over the first RAT access type and the second RATaccess type.
 18. The UE of claim 10, wherein the UE registers with afirst Public Land Mobile Network (PLMN) over the first RAT access typeand a second PLMN over the second RAT access type.